CD BIT 75/CD BIT 75.iso/Software/mysql-4.0.22-win/data1.cab/Documentation/Docs/ChangeLog

Text File | 2004-10-28 | 55.2 KB | 1,450 lines

ChangeSet
  1.2048.1.2 04/10/27 21:51:27 [e-mail] +2 -0
   - Applied some Windows portability fixes for myisampack.c and sql_handler.cc
    (backports from fixes made in 4.1)

  sql/sql_handler.cc
    1.45 04/10/27 21:51:24 [e-mail] +1 -7
     - removed some unused variables
     - added a (byte*) cast to fix a compile error on Windows (backport of a
       fix made in 4.1)

  myisam/myisampack.c
    1.34 04/10/27 21:51:24 [e-mail] +1 -1
     - replaced "1ULL" with "((ulonglong)1)" to resolve a compile error on
       Windows

ChangeSet
  1.2051 04/10/27 13:44:31 [e-mail] +1 -0
  texi2html:
    Updated version of texi2html so that 4.0.22 HTML manual doesn't turn out all goofy.

  Docs/Support/texi2html
    1.8 04/10/27 13:43:37 [e-mail] +53 -45
    Updated version of texi2html so that 4.0.22 HTML manual doesn't turn out all goofy.

ChangeSet
  1.2048.1.1 04/10/27 18:57:49 [e-mail] +3 -0
  Fix when compiling without InnoDB

  mysql-test/t/innodb-lock.test
    1.4 04/10/27 18:57:48 [e-mail] +5 -0
    Fix when compiling without InnoDB

  mysql-test/r/innodb-lock.result
    1.4 04/10/27 18:57:48 [e-mail] +1 -0
    Fix when compiling without InnoDB

ChangeSet
  1.2049 04/10/27 17:54:10 [e-mail] +1 -0
  Change 'Build-tools/mysql-copyright' to ensure the receiving machines will build
  without trying to re-run autotools.
  (Backport from 4.1.7 for 4.0.22)

  Build-tools/mysql-copyright
    1.18 04/10/27 17:54:09 [e-mail] +14 -7
    The top level Makefile will try to re-run the autotools unless the timestamps of the
    relevant files are in truly ascending order. Ensure this order!
    (Backport from 4.1.7 for 4.0.22)

  BitKeeper/deleted/.del-innodb-lock-master.opt~f76a4a1999728f87
    1.2 04/10/27 18:34:10 [e-mail] +0 -0
    Delete: mysql-test/t/innodb-lock-master.opt

ChangeSet
  1.2048 04/10/27 13:33:11 [e-mail] +9 -0
  Backport innodb_max_purge_lag from 4.1

  sql/set_var.cc
    1.60 04/10/27 13:33:07 [e-mail] +4 -0
    Add global variable innodb_max_purge_lag.

  sql/mysqld.cc
    1.518 04/10/27 13:33:07 [e-mail] +6 -0
    Add startup option innodb_max_purge_lag,
    with default value 0 (meaning infinite, disabling the feature).

  sql/ha_innodb.h
    1.64 04/10/27 13:33:07 [e-mail] +1 -0
    Add configuration parameter srv_max_purge_lag.

  innobase/trx/trx0rseg.c
    1.4 04/10/27 13:33:07 [e-mail] +6 -1
    Initialize trx_sys->rseg_history_len at InnoDB start-up.

  innobase/trx/trx0purge.c
    1.17 04/10/27 13:33:07 [e-mail] +38 -0
    Update trx_sys->rseg_history_len.
    trx_purge(): Compute srv_dml_needed_delay from srv_max_purge_lag
    and trx_sys->rseg_history_len.

  innobase/srv/srv0srv.c
    1.76 04/10/27 13:33:07 [e-mail] +6 -0
    Define global variable srv_dml_needed_delay.
    Define configuration parameter srv_max_purge_lag.

  innobase/row/row0mysql.c
    1.74 04/10/27 13:33:07 [e-mail] +17 -0
    Add row_mysql_delay_if_needed() for delaying INSERTs, UPDATEs and
    DELETEs for srv_dml_needed_delay microseconds.

  innobase/include/trx0sys.h
    1.12 04/10/27 13:33:07 [e-mail] +4 -0
    Add trx_sys->rseg_history_len

  innobase/include/srv0srv.h
    1.34 04/10/27 13:33:07 [e-mail] +2 -0
    Add configuration parameter srv_max_purge_lag.
    Add global variable srv_dml_needed_delay.

ChangeSet
  1.2044.1.7 04/10/22 22:51:04 [e-mail] +3 -0
  postreview fixes

  sql/sql_cache.cc
    1.63 04/10/22 22:51:02 [e-mail] +2 -2
    difine used instead of constant
    typo fixed

  sql/sql_base.cc
    1.186 04/10/22 22:51:02 [e-mail] +3 -2
    difine used instead of constant

  sql/mysql_priv.h
    1.229 04/10/22 22:51:02 [e-mail] +1 -0
    constant definition

ChangeSet
  1.2044.3.3 04/10/22 19:27:43 [e-mail] +1 -0
  Part of fix for bug #6081 "Call to deprecated mysql_create_db() function
  crashes server"

  (in 4.0 we fix only connection stalling in case of error, crash itself is
  fixed in 4.1, the test case for this code is also there).

  sql/sql_parse.cc
    1.384.1.1 04/10/22 19:27:34 [e-mail] +6 -2
    Handling of COM_CREATE_DB, COM_DROP_DB:
    We should call send_error() if mysql_create_db or mysql_drop_db
    return error (like we do it for SQL versions of these commands).

ChangeSet
  1.2044.3.2 04/10/22 10:45:00 [e-mail] +1 -0
  os0file.c:
    Add typecast from ulint to ssize_t in pread and pwrite, so that the type is according to the Linux man page; this will probably not help to fix the HP-UX 32-bit pwrite failure, since the compiler should do the appropriate typecasts anyway

  innobase/os/os0file.c
    1.78 04/10/22 10:44:23 [e-mail] +4 -4
    Add typecast from ulint to ssize_t in pread and pwrite, so that the type is according to the Linux man page; this will probably not help to fix the HP-UX 32-bit pwrite failure, since the compiler should do the appropriate typecasts anyway

ChangeSet
  1.2044.3.1 04/10/22 00:25:57 [e-mail] +2 -0
  row0mysql.c, row0ins.c:
    Fix bug #5961: release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users

  innobase/row/row0mysql.c
    1.73 04/10/22 00:25:29 [e-mail] +2 -2
    Fix bug #5961: release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users

  innobase/row/row0ins.c
    1.39 04/10/22 00:25:29 [e-mail] +17 -0
    Fix bug #5961: release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users

ChangeSet
  1.2044.1.5 04/10/21 23:56:12 [e-mail] +4 -0
  Check of temporary tables hiding for query fetched from QC (BUG#6084)

  sql/sql_cache.h
    1.22 04/10/21 23:56:02 [e-mail] +3 -0
    Key length now stored in table record of query cache

  sql/sql_cache.cc
    1.62 04/10/21 23:56:02 [e-mail] +31 -1
    Check of temporary tables hiding for query fetched from QC

  mysql-test/t/query_cache.test
    1.30 04/10/21 23:56:02 [e-mail] +12 -0
    hiding real table stored in query cache by temporary table

  mysql-test/r/query_cache.result
    1.29 04/10/21 23:56:02 [e-mail] +13 -0
    hiding real table stored in query cache by temporary table

ChangeSet
  1.2044.1.4 04/10/20 16:04:28 [e-mail] +6 -0
  Fix test case for innodb-lock

  mysql-test/t/innodb-lock-master.opt
    1.1 04/10/20 16:04:26 [e-mail] +1 -0

  sql/sql_base.cc
    1.185 04/10/20 16:04:26 [e-mail] +2 -0
    More debug information

  sql/mysqld.cc
    1.517 04/10/20 16:04:26 [e-mail] +1 -1
    Enable innodb_table_locks as default, as otherwise there is a possibility for deadlocks

  mysys/thr_lock.c
    1.37 04/10/20 16:04:26 [e-mail] +10 -2
    More debugging information

  mysql-test/t/innodb-lock.test
    1.3 04/10/20 16:04:26 [e-mail] +29 -18
    Fix test case (old one didn't test things correctly)

  mysql-test/t/innodb-lock-master.opt
    1.0 04/10/20 16:04:26 [e-mail] +0 -0
    BitKeeper file /home/my/mysql-4.0/mysql-test/t/innodb-lock-master.opt

  mysql-test/r/innodb-lock.result
    1.3 04/10/20 16:04:26 [e-mail] +19 -11
    Fix test case (old one didn't test things correctly)

ChangeSet
  1.2044.2.1 04/10/20 11:24:08 [e-mail] +8 -0
  Code cleanups (done during review of new code)
  Rename innodb_table_locks_old_behavior -> innodb_table_locks
  Set innodb_table_locks to off by default to get same behaviour as in MySQL 4.0.20
  (This means that Innodb ignore table locks by default, which makes it easier to combine MyISAM and InnoDB to simulate a transaction)

  sql/sql_class.h
    1.189 04/10/20 11:24:07 [e-mail] +1 -1
    Rename innodb_table_locks_old_behavior -> innodb_table_locks

  sql/set_var.cc
    1.59 04/10/20 11:24:07 [e-mail] +4 -4
    Rename innodb_table_locks_old_behavior -> innodb_table_locks

  sql/mysqld.cc
    1.516 04/10/20 11:24:07 [e-mail] +5 -5
    Rename innodb_table_locks_old_behavior -> innodb_table_locks
    Set this off by default to get same behaviour as in MySQL 4.0.20


  sql/ha_innodb.cc
    1.224 04/10/20 11:24:07 [e-mail] +1 -1
    Rename innodb_table_locks_old_behavior -> innodb_table_locks

  mysql-test/t/innodb-lock.test
    1.2 04/10/20 11:24:07 [e-mail] +45 -1
    new test case

  mysql-test/r/innodb-lock.result
    1.2 04/10/20 11:24:07 [e-mail] +26 -0
    new test case

  myisam/myisampack.c
    1.33 04/10/20 11:24:07 [e-mail] +5 -7
    Simplify code

  libmysql/libmysql.c
    1.153.1.1 04/10/20 11:24:07 [e-mail] +4 -6
    Use ulong instead of unsigned long
    Reuse _dig_vec()

ChangeSet
  1.2044.1.2 04/10/19 18:58:53 [e-mail] +1 -0
  trx0rec.c:
    test

  innobase/trx/trx0rec.c
    1.13 04/10/19 18:58:30 [e-mail] +1 -1
    test

ChangeSet
  1.2044.1.1 04/10/19 07:44:20 [e-mail] +1 -0
  libmysql.c:
    Add note to mysql_hex_string() comment.

  libmysql/libmysql.c
    1.154 04/10/19 07:43:32 [e-mail] +3 -0
    Add note to mysql_hex_string() comment.

ChangeSet
  1.2045 04/10/19 11:54:33 [e-mail] +1 -0
  fixed retsult code

  sql/sql_parse.cc
    1.385 04/10/19 11:54:25 [e-mail] +1 -1
    fixed retsult code

ChangeSet
  1.2044 04/10/19 09:50:47 [e-mail] +1 -0
  libmysql.c:
    New function mysql_hex_string()

  libmysql/libmysql.c
    1.153 04/10/19 09:50:28 [e-mail] +33 -0
    New function mysql_hex_string()

ChangeSet
  1.2022.9.3 04/10/17 18:44:51 dellis@goetia.(none) +1 -0
  mysqld.cc:
    BUG #5731 key_buffer_size not properly restricted to 4GB; use UINT_MAX32 for clarity.

  sql/mysqld.cc
    1.512.1.2 04/10/17 18:44:24 dellis@goetia.(none) +1 -1
    BUG #5731 key_buffer_size not properly restricted to 4GB; use UINT_MAX32 for clarity.

ChangeSet
  1.2041 04/10/15 23:16:02 [e-mail] +1 -0
  texi2html:
    Change parsing of @image argument.

  Docs/Support/texi2html
    1.7 04/10/15 23:15:27 [e-mail] +1 -1
    Change parsing of @image argument.

ChangeSet
  1.2038.2.1 04/10/15 15:33:30 [e-mail] +1 -0
  the $^ directive is a GNU make extension and not really needed here
  so lets get rid of it (Bug #6112)

  configure.in
    1.316 04/10/15 15:33:27 [e-mail] +2 -2
    the $^ directive is a GNU make extension and not really needed here
    so lets get rid of it (Bug #6112)

ChangeSet
  1.2028.1.1 04/10/14 20:02:56 [e-mail] +2 -0
  BUG#5625 - MyISAM Index corruption on ALTER TABLE x ENABLE KEYS due to full tmpdir.
  Added a try to a normal repair() if repair_by_sort() failed.
  This was not done with ENABLE KEYS and OPTIMIZE TABLE.
  Fixed error code handling in mysql_alter_table().

  sql/sql_table.cc
    1.187.1.1 04/10/14 20:02:55 [e-mail] +1 -1
    BUG#5625 - MyISAM Index corruption on ALTER TABLE x ENABLE KEYS due to full tmpdir.
    Added a translation from 'bool' return value to '< 0' error indication,
    which is used within mysql_execute_command() and must as such be
    handed over by mysql_alter_table(). A returncode >= 0 is interpreted
    as 'I have already called send_ok()'.

  sql/ha_myisam.cc
    1.131.1.1 04/10/14 20:02:55 [e-mail] +16 -2
    BUG#5625 - MyISAM Index corruption on ALTER TABLE x ENABLE KEYS due to full tmpdir.
    Added a try to a normal repair() if repair_by_sort() failed.
    This was not done with ENABLE KEYS and OPTIMIZE TABLE.

ChangeSet
  1.2039 04/10/13 22:54:21 [e-mail] +4 -0
  Added startup option and settable session variable
  innodb_table_locks_old_behavior: do not acquire an
  InnoDB table lock for LOCK TABLES, as in mysql-4.0.18
  and earlier.

  sql/sql_class.h
    1.188 04/10/13 22:54:17 [e-mail] +3 -0
    Added innodb_table_locks_old_behavior

  sql/set_var.cc
    1.58 04/10/13 22:54:17 [e-mail] +4 -0
    Added innodb_table_locks_old_behavior

  sql/mysqld.cc
    1.514 04/10/13 22:54:17 [e-mail] +6 -1
    Added innodb_table_locks_old_behavior

  sql/ha_innodb.cc
    1.223 04/10/13 22:54:17 [e-mail] +2 -1
    Do not acquire an InnoDB table lock for LOCK TABLES if
    innodb_table_locks_old_behavior is enabled.

ChangeSet
  1.2038 04/10/12 18:12:00 [e-mail] +1 -0
  ha_innodb.cc:
    Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous value HA_ERR_CANNOT_ADD_FOREIGN, but misleading still; we should introduce to 5.0 a proper MySQL error code

  sql/ha_innodb.cc
    1.222 04/10/12 18:11:50 [e-mail] +1 -1
    Change error code to HA_ERR_ROW_IS_REFERENCED if we cannot DROP a parent table referenced by a FOREIGN KEY constraint; this error number is less misleading than the previous value HA_ERR_CANNOT_ADD_FOREIGN, but misleading still; we should introduce to 5.0 a proper MySQL error code

ChangeSet
  1.2022.14.1 04/10/11 11:01:38 [e-mail] +3 -0
  Fix for BUG#5949 "error code 1223 in binlog when using innobackup":
  when one connection had done FLUSH TABLES WITH READ LOCK, some updates, and then COMMIT,
  it was accepted but my_error() was called and so, while client got no error, error was logged in binlog.
  We now don't call my_error() in this case; we assume the connection know what it does.
  This problem was specific to 4.0.21. The change is needed to make replication work with existing versions of innobackup.

  mysql-test/t/rpl_commit_after_flush.test
    1.1 04/10/11 11:01:36 [e-mail] +17 -0

  mysql-test/r/rpl_commit_after_flush.result
    1.1 04/10/11 11:01:36 [e-mail] +13 -0

  sql/lock.cc
    1.48 04/10/11 11:01:36 [e-mail] +8 -2
    If a connection has done FLUSH TABLES WITH READ LOCK and now is doing COMMIT, don't give error
    (applies only if it's the same connection; others' COMMITs are still blocked).

  mysql-test/t/rpl_commit_after_flush.test
    1.0 04/10/11 11:01:36 [e-mail] +0 -0
    BitKeeper file /home/mysql_src/mysql-4.0/mysql-test/t/rpl_commit_after_flush.test

  mysql-test/r/rpl_commit_after_flush.result
    1.0 04/10/11 11:01:36 [e-mail] +0 -0
    BitKeeper file /home/mysql_src/mysql-4.0/mysql-test/r/rpl_commit_after_flush.result

ChangeSet
  1.2036 04/10/09 14:13:40 [e-mail] +1 -0
  trx0rec.c:
    Fix bug #5960: if one updated a column so that its size changed, or updated it to an externally stored (TEXT or BLOB) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row

  innobase/trx/trx0rec.c
    1.12 04/10/09 14:13:12 [e-mail] +17 -11
    Fix bug #5960: if one updated a column so that its size changed, or updated it to an externally stored (TEXT or BLOB) value, then ANOTHER externally stored column would show up as 512 bytes of good data + 20 bytes of garbage in a consistent read that fetched the old version of the row

ChangeSet
  1.2035 04/10/08 16:32:56 [e-mail] +1 -0
  Using MySQL 4.0 with privilege tables from 5.0 caused a crash.
  (Fixed this by backporting some logic from 4.1)

  sql/sql_acl.cc
    1.130 04/10/08 16:32:54 [e-mail] +37 -21
    Using MySQL 4.0 with privilege tables from 5.0 caused a crash.
    (Fixed this by backporting some logic from 4.1)

ChangeSet
  1.2034 04/10/07 20:30:30 [e-mail] +2 -0
  Fixed Bug#5575, mysqlhotcopy is broken when using --noindices

  BitKeeper/etc/logging_ok
    1.326.1.1 04/10/07 20:30:30 [e-mail] +1 -0
    Logging to [e-mail] accepted

  scripts/mysqlhotcopy.sh
    1.46 04/10/07 20:30:26 [e-mail] +4 -4
    Fixed Bug#5575, mysqlhotcopy is broken when using --noindices

ChangeSet
  1.2033 04/10/07 15:58:47 [e-mail] +3 -0
  InnoDB: tolerate system clock glitches a little better
  in the error monitor thread.  (Bug #5898)

  innobase/sync/sync0arr.c
    1.20 04/10/07 15:58:43 [e-mail] +7 -8
    sync_array_print_long_waits(): return error status

  innobase/srv/srv0srv.c
    1.75 04/10/07 15:58:43 [e-mail] +16 -4
    srv_error_monitor_thread(): Keep track on successive fatal timeouts,
    and crash the server only if the timeouts have been exceeded for
    several times in succession.

  innobase/include/sync0arr.h
    1.6 04/10/07 15:58:42 [e-mail] +3 -1
    sync_array_print_long_waits(): return error status

ChangeSet
  1.2031 04/10/06 17:20:39 [e-mail] +3 -0
  Code cleanups while doing review of pushed code

  sql/sql_handler.cc
    1.44 04/10/06 17:20:35 [e-mail] +31 -35
    Change mode to uint (as it's a bitmap)
    Fixed DBUG_PRINT to use same format as other MySQL code

  sql/mysql_priv.h
    1.228 04/10/06 17:20:35 [e-mail] +1 -1
    Change mode to uint (as it's a bitmap)

  myisam/mi_locking.c
    1.32 04/10/06 17:20:35 [e-mail] +18 -14
    More comments

ChangeSet
  1.2022.13.1 04/10/06 01:24:21 [e-mail] +7 -0
  Reverted patch for new usage of open_count as it caused more problems than it solved
  Cleaned up patch for checking locks for multi-table updates

  sql/sql_update.cc
    1.103 04/10/06 01:24:19 [e-mail] +67 -43
    Cleaned up (and made it more secure) patch for checking locks for multi-table updates

  sql/sql_table.cc
    1.186.1.1 04/10/06 01:24:19 [e-mail] +1 -5
    No need to unlock after failed call to external_lock()

  sql/sql_acl.cc
    1.129 04/10/06 01:24:19 [e-mail] +1 -1
    Removed compiler warning

  sql/handler.cc
    1.111 04/10/06 01:24:19 [e-mail] +1 -1
    Removed compiler warning

  sql/ha_myisam.cc
    1.132 04/10/06 01:24:19 [e-mail] +4 -22
    Reverted patch for new usage of open_counts

  myisam/mi_locking.c
    1.31 04/10/06 01:24:19 [e-mail] +34 -83
    Reverted patch for new usage of open_counts

  myisam/mi_close.c
    1.15 04/10/06 01:24:19 [e-mail] +7 -2
    Reverted patch for new usage of open_counts

ChangeSet
  1.2022.1.19 04/10/05 21:19:40 hf@deer.(none) +1 -0
  Fix for #5730 (Query cache crashes server)
  Recusive part leads to stack overflow

  sql/sql_cache.cc
    1.61 04/10/05 21:19:29 hf@deer.(none) +37 -38
    Recursion removed from Query_cache::allocate_data_chain

ChangeSet
  1.2022.12.1 04/10/05 14:47:10 [e-mail] +1 -0
  Fix for wrongly calculated Examined_rows in 4.0 UNION's.

  sql/sql_union.cc
    1.50 04/10/05 14:47:03 [e-mail] +7 -2
    Fixing a non-critical bug in 4.0 UNION's which results in erronously
    calculated number o fexamined rows. This value is displayed in the
    slow query log.

    This is a bug number #5879.


ChangeSet
  1.2022.10.3 04/10/04 20:07:49 [e-mail] +1 -0
  Bug #5829      mysqlimport garbles path of the file to be imported

  Original code was checking ! unix_socket for local_file flag.  This doesn't work and so was removed.  Now
  to import a local file, you must use the --local command line option.

  mysqlimport.c:
    Removed check of unix_socket to set local_file

ChangeSet
  1.2022.10.2 04/10/04 23:26:42 [e-mail] +3 -0
  patch fixing after review on patch-fixing of
  Bug #5492
  "set @@session.read_rnd_buffer_size=33554432" crashes server on query

  1. added warning comments for uint3korr (need one more byte allocated)
  2. unsigned long in uint3korr was replaced by unsigned int to
     avoid problems on 64-bits platforms
  3. shorten warning comments in init_rr_cache in sql/records.cc

  sql/records.cc
    1.23 04/10/04 23:26:39 [e-mail] +1 -6
    shorten warning comments for my_malloc_lock in init_rr_cache

  include/my_global.h
    1.69 04/10/04 23:26:39 [e-mail] +7 -1
    1. added warning comments for uint3korr (need one more byte allocated)
    2. unsigned long in uint3korr was replaced by unsigned int to
       avoid problems on 64-bits platforms

  include/config-win.h
    1.36 04/10/04 23:26:39 [e-mail] +7 -1
    1. added warning comments for uint3korr (need one more byte allocated)
    2. unsigned long in uint3korr was replaced by unsigned int to
       avoid problems on 64-bits platforms

  client/mysqlimport.c
    1.35 04/10/04 20:01:32 [e-mail] +3 -5
    Removed check of unix_socket to set local_file

ChangeSet
  1.2025 04/10/04 16:24:37 [e-mail] +2 -0
  InnoDB: make ALTER TABLE to work on table names containing '#' (Bug #5856)

  innobase/row/row0mysql.c
    1.72 04/10/04 16:24:34 [e-mail] +1 -0
    row_drop_table_for_mysql(): Remove a memory leak

  innobase/dict/dict0dict.c
    1.60 04/10/04 16:24:33 [e-mail] +16 -6
    dict_strip_comments(): do not look for comments within quotes (Bug #5856)

ChangeSet
  1.2022.9.2 04/10/03 10:00:26 dellis@goetia.(none) +2 -0
  mysqld.cc:
    BUG #5731 Restrict key_buffer_size to 4GB on 64 bit platforms

  BitKeeper/etc/logging_ok
    1.327 04/10/03 10:00:26 dellis@goetia.(none) +1 -0
    Logging to [e-mail] accepted

  sql/mysqld.cc
    1.512.1.1 04/10/03 10:00:06 dellis@goetia.(none) +1 -1
    BUG #5731 Restrict key_buffer_size to 4GB on 64 bit platforms

ChangeSet
  1.2022.7.1 04/10/03 00:20:47 [e-mail] +7 -0
  Bug#4118: multi-table UPDATE takes WRITE lock on read table
    Ensures that WRITE lock is not obtained on all tables referenced.

  sql/sql_yacc.yy
    1.232 04/10/03 00:20:46 [e-mail] +10 -2
    Bug#4118
      Split multi-update to its own case statement in sql_parse.cc

  sql/sql_update.cc
    1.102 04/10/03 00:20:46 [e-mail] +90 -14
    Bug#4118
      Overview of locking checking:
        1. Open and acquire READ lock
        2. Check to see which tables need WRITE lock
        3. Unlock tables and relock

  sql/sql_parse.cc
    1.382.1.1 04/10/03 00:20:46 [e-mail] +17 -12
    Bug#4118
      Split multi-update to its own case statement in sql_parse.cc

  mysql-test/t/multi_update.test
    1.36 04/10/03 00:20:46 [e-mail] +0 -2
    Bug#4118
      Fix test

  mysql-test/t/lock_multi.test
    1.5 04/10/03 00:20:46 [e-mail] +24 -0
    Bug#4118
      New test for multi-update locking

  mysql-test/r/multi_update.result
    1.34 04/10/03 00:20:46 [e-mail] +0 -1
    Bug#4118
      Fix test

  mysql-test/r/lock_multi.result
    1.6 04/10/03 00:20:45 [e-mail] +12 -0
    Bug#4118
      New test for multi-update locking

ChangeSet
  1.2022.6.1 04/10/01 16:23:54 [e-mail] +3 -0
  delete.result, delete.test:
    A fix (bug #5733: Table handler error with self-join multi-table DELETE).
  records.cc:
    A fix (bug #5733: Table handler error with self-join multi-table DELETE).

  mysql-test/r/delete.result
    1.10 04/10/01 16:23:18 [e-mail] +11 -0
    A fix (bug #5733: Table handler error with self-join multi-table DELETE).

  mysql-test/t/delete.test
    1.11 04/10/01 16:23:08 [e-mail] +10 -0
    A fix (bug #5733: Table handler error with self-join multi-table DELETE).

  sql/records.cc
    1.21.1.1 04/10/01 16:22:22 [e-mail] +18 -9
    ]A fix (bug #5733: Table handler error with self-join multi-table DELETE).

ChangeSet
  1.2022.1.15 04/09/30 19:05:33 [e-mail] +1 -0
  Solve compile problem for 4.0.22 on hpita2. (Backport of a 4.1 change)

  sql/mysqld.cc
    1.513 04/09/30 19:05:32 [e-mail] +6 -6
    Replace 'sete_id(_)' calls by 'setre_id(-1,_)' calls, as the former
    have no prototypes on some platforms. (Backport of a 4.1 change)

ChangeSet
  1.2022.5.1 04/09/29 23:25:32 [e-mail] +1 -0
  Fix for BUG#4785 part two:
  * If at least one of indexes is disabled, use data file size as an estimate
    for key file size.
  * Added handling for joined tables.

  myisam/myisampack.c
    1.32 04/09/29 23:25:28 [e-mail] +30 -8
    Fix for BUG#4785 part two:
    * If at least one of indexes is disabled, use data file size as an estimate
      for key file size.
    * Added handling for joined tables.

ChangeSet
  1.1996.2.1 04/09/27 00:50:00 [e-mail] +7 -0
  Fix for bug #4131 "TIMESTAMP columns missing minutes and seconds when
  using GROUP BY"
  Now we are setting Field_timestamp::field_length to 19 in open_table()
  if we are in new mode (and we are restoring it back when we are coming
  back to normal mode). This also should solve potential problems with
  some of LOAD DATA INFILE and SELECT * INTO in this mode.

  sql/table.h
    1.46 04/09/27 00:49:58 [e-mail] +8 -0
    Added TABLE::timestamp_mode field for saving information whenever we set
    field_length members of table's TIMESTAMP fields to 19 (to honor
    new_mode) or they have original values.

  sql/sql_parse.cc
    1.381.1.1 04/09/27 00:49:58 [e-mail] +11 -0
    Now when we are creating TIMESTAMP(19) fields by default in --new mode,
    otherwise we will have unaligned behavior between ALTER and CREATE.

  sql/sql_base.cc
    1.182.1.1 04/09/27 00:49:58 [e-mail] +25 -0
    If --new mode is in effect all TIMESTAMP fields should pretend that they
    have length of 19. We are achieving this by setting
    Field_timestamp::field_length to 19 (or original value) in open_table().
    We are using TABLE::timestamp_mode variable for avoiding of unnecessary
    looping over all fields of the table and setting field_length if table
    was used with same new_mode value before.

    Note: We do not introduce general framework for setting up Field objects
    for usage with current THD here because this fix is only needed in 4.0
    and Monty said that we will also remove looping over all fields when
    updating table_name member at some point. This more general framework
    will also complicate nice optimization with avoiding of unneeded looping.

  sql/field.h
    1.58 04/09/27 00:49:58 [e-mail] +12 -1
    Added Field_timestamp::orig_field_length member for saving original
    field_length value, because this member can be modified if new_mode
    is in effect.
    Field_timestamp::make_field() is no longer needed because we are setting
    field_length to 19 if we are in --new mode now.

  sql/field.cc
    1.95 04/09/27 00:49:58 [e-mail] +5 -19
    Added Field_timestamp::orig_field_length member for saving original
    field_length value, because this member can be modified if new_mode is
    in effect.
    Lot of Field_timestamp code simplified and Field_timestamp::make_field()
    is no longer needed because we are setting field_length to 19 if we are
    in --new mode now.

  mysql-test/t/type_timestamp.test
    1.12 04/09/27 00:49:58 [e-mail] +32 -0
    Added test for bug #4131 'TIMESTAMP columns missing minutes and seconds
    when using GROUP BY' and other --new mode related behavior.

  mysql-test/r/type_timestamp.result
    1.14 04/09/27 00:49:58 [e-mail] +51 -9
    Added test for bug #4131 'TIMESTAMP columns missing minutes and seconds
    when using GROUP BY' and other --new mode related behavior.

ChangeSet
  1.2022.1.12 04/09/26 15:27:13 [e-mail] +2 -0
  added --without-man option similar to --without-docs
  (part of BUG#5379)

  configure.in
    1.315 04/09/26 15:27:10 [e-mail] +15 -0
    added --without-man option similar to --without-docs
    (part of BUG#5379)

  Makefile.am
    1.52 04/09/26 15:27:10 [e-mail] +1 -1
    added --without-man option similar to --without-docs
    (part of BUG#5379)

ChangeSet
  1.2022.1.11 04/09/26 15:24:57 [e-mail] +2 -0
  make --with-openssl work with parameters as expected,
  old options for include path and library settings still
  work for backwards compatibility
  (fix for BUG #5494)

  BitKeeper/etc/logging_ok
    1.326 04/09/26 15:24:56 [e-mail] +1 -0
    Logging to [e-mail] accepted

  acinclude.m4
    1.99 04/09/26 15:24:43 [e-mail] +21 -2
    make --with-openssl work with parameters as expected,
    old options for include path and library settings still
    work for backwards compatibility
    (fix for BUG #5494)

ChangeSet
  1.2022.4.2 04/09/25 18:43:07 [e-mail] +1 -0
  Bug #5539      SHOW DATABASES LIKE and symlinks

  sql_show.cc:
    Made change suggested by Serge. REmoved else in mysql_find_files so symlink files fall through to the wildcard check

  sql/sql_show.cc
    1.127 04/09/25 18:40:47 [e-mail] +5 -10
    Made change suggested by Serge. REmoved else in mysql_find_files so symlink files fall through to the wildcard check

ChangeSet
  1.2007.11.1 04/09/24 18:39:25 [e-mail] +10 -0
  BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
  BUG#4335 - one name can be handler open'ed many times.
  Reworked the HANDLER functions and interface.
  Using a HASH to store information on open tables that
  survives FLUSH TABLE.
  HANDLER tables alias names must now be unique, though it
  is allowed in 4.0 to qualify them with the database name
  of the base table.

  sql/sql_table.cc
    1.183.1.1 04/09/24 18:39:23 [e-mail] +3 -3
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    replaced mysql_ha_close() by the better named
    function mysql_ha_flush() with readable options.

  sql/sql_handler.cc
    1.43 04/09/24 18:39:23 [e-mail] +450 -166
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Completely reworked the handler functions.
    Added an introducing comment, describing the new functionality.

  sql/sql_class.h
    1.185.1.1 04/09/24 18:39:23 [e-mail] +1 -0
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Added the handler tables HASH to THD.

  sql/sql_class.cc
    1.111 04/09/24 18:39:23 [e-mail] +7 -8
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Added initialization for the handler tables hash.
    Changed the handler tables clean-up code.
    Unreleted to bug: Changed the order of THD initialization
    to avoid warning messages on Linux with gcc.

  sql/sql_base.cc
    1.183 04/09/24 18:39:23 [e-mail] +3 -3
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Replaced mysql_ha_close_list() by the better named
    function mysql_ha_flush() with readable options.

  sql/mysql_priv.h
    1.227 04/09/24 18:39:23 [e-mail] +7 -4
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Reworked the handler interface.

  mysql-test/t/handler.test
    1.16 04/09/24 18:39:23 [e-mail] +204 -0
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Moved pure handler tests from flush_table.test to here.

  mysql-test/t/flush_table.test
    1.6 04/09/24 18:39:23 [e-mail] +23 -61
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Moved pure handler tests to handler.test.
    Added new tests.

  mysql-test/r/handler.result
    1.16 04/09/24 18:39:23 [e-mail] +244 -0
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Moved pure handler test results from flush_table.result to here.

  mysql-test/r/flush_table.result
    1.3 04/09/24 18:39:23 [e-mail] +43 -58
    BUG#4286 - HANDLER tables are closed by FLUSH TABLE(S).
    BUG#4335 - one name can be handler open'ed many times.
    Moved pure handler test results to handler.result.
    Added the new test results.

ChangeSet
  1.2022.1.10 04/09/24 11:54:37 [e-mail] +6 -0
  Fix for BUG#3248 "Doc says MyISAM warns if disk full but it does not":
  we force the message to the error log, and we make it more informative;
  we treat EDQUOT like ENOSPC.

  sql/mysqld.cc
    1.512 04/09/24 11:54:28 [e-mail] +2 -3
    If ME_NOREFRESH, we write message to error log, even if it has been saved for client (because if operation
    is hanging, the message does not get to client now; example is MyISAM waiting for free disk space).

  mysys/mysys_priv.h
    1.11 04/09/24 11:54:27 [e-mail] +8 -0
    Define EDQUOT when it does not exist. Finally decided to put it here after discussion with Monty:
    as this constant is used only in 3 files only in mysys/, I don't make it visible everywhere
    (there currently is no file of choice for such defines; my_base.h does not contain any).
    Using a value which never happens avoids collisions.

  mysys/my_write.c
    1.9 04/09/24 11:54:27 [e-mail] +3 -2
    Treat EDQUOT like ENOSPC.

  mysys/my_pread.c
    1.9 04/09/24 11:54:27 [e-mail] +5 -4
    Treat EDQUOT like ENOSPC.

  mysys/my_fstream.c
    1.7 04/09/24 11:54:27 [e-mail] +8 -6
    Treat EDQUOT like ENOSPC.

  mysys/errors.c
    1.14 04/09/24 11:54:27 [e-mail] +1 -1
    more informative message

ChangeSet
  1.2022.4.1 04/09/24 09:00:14 [e-mail] +1 -0
  Bug #5539      SHOW DATABASES LIKE and symlinks

  sql_show.cc:
    Added wild card check to symdir block in mysql_find_files

  sql/sql_show.cc
    1.126 04/09/24 08:58:20 [e-mail] +2 -1
    Added wild card check to symdir block in mysql_find_files

ChangeSet
  1.2022.1.8 04/09/23 17:53:46 [e-mail] +1 -0
  os0file.c:
    Added #ifdef around is_set in os_aio_print

  innobase/os/os0file.c
    1.77 04/09/23 17:52:24 [e-mail] +2 -0
    Added #ifdef around is_set in os_aio_print

ChangeSet
  1.2007.1.11 04/09/23 14:43:31 [e-mail] +1 -0
  Fix for BUG#5711 "replication SQL thread does not abort on SQL syntax error":
  in net_printf(), we fill net->last_* variables for the slave SQL thread to know the error.

  sql/net_pkg.cc
    1.33 04/09/23 14:43:29 [e-mail] +4 -0
    in net_printf(), store the error in net->last_*, so that slave SQL thread can be aware there was an error reported by net_printf()
    (which is what yacc uses for "you have an error in your syntax").

ChangeSet
  1.2020.1.1 04/09/22 16:29:15 [e-mail] +4 -0
  Fix for BUG#4785:
   * myisampack leaves key_file_length value from original table
   * myisamchk uses this value when calculating key file pointer length

  myisam/myisampack.c
    1.31 04/09/22 16:29:11 [e-mail] +5 -1
    Fix for BUG#4785:
     * myisampack leaves key_file_length value from original table
     * myisamchk uses this value when calculating key file pointer length

  myisam/mi_create.c
    1.33 04/09/22 16:29:11 [e-mail] +9 -4
    Fix for BUG#4785:
     * myisampack leaves key_file_length value from original table
     * myisamchk uses this value when calculating key file pointer length

  myisam/mi_check.c
    1.133 04/09/22 16:29:11 [e-mail] +1 -1
    Fix for BUG#4785:
     * myisampack leaves key_file_length value from original table
     * myisamchk uses this value when calculating key file pointer length

  include/myisam.h
    1.55 04/09/22 16:29:11 [e-mail] +1 -0
    Fix for BUG#4785:
     * myisampack leaves key_file_length value from original table
     * myisamchk uses this value when calculating key file pointer length

ChangeSet
  1.2022.3.1 04/09/22 11:28:37 [e-mail] +1 -0
  Bug#5655 - mysqldump fields-escaped-by behaviour
    Fix initialization

  client/mysqldump.c
    1.115 04/09/22 11:28:33 [e-mail] +1 -1
    Bug#5655 - mysqldump fields-escaped-by behaviour
      Fix for parameter

ChangeSet
  1.2022.1.5 04/09/20 17:58:11 [e-mail] +1 -0
  When coyright text is changed, autotools must be run after all
  other actions, as otherwise timestamps of "config.h.in" will
  cause re-run on compilation machine (fatal version problem!).

  Build-tools/mysql-copyright
    1.17 04/09/20 17:58:10 [e-mail] +112 -28
    1) Ensure that autotools are run as last action, after copyright
    change, for proper timestamps.
    2) Move the trimming of subtrees to an own function "trim_the_fat".
    3) Align 4.0 and 4.1 versions.

ChangeSet
  1.2022.2.1 04/09/19 16:15:01 [e-mail] +1 -0
  A fix (Bug #5415: Table marked as crashed after DELETE queries).

  sql/sql_delete.cc
    1.108 04/09/19 16:14:59 [e-mail] +2 -0
    A fix (Bug #5415: Table marked as crashed after DELETE queries).

ChangeSet
  1.2022.1.3 04/09/19 14:48:41 [e-mail] +1 -0
  Change www.mysql.com -> dev.mysql.com in a reference to
  how to resolve stack trace documentation.

  sql/stacktrace.c
    1.14 04/09/19 14:48:40 [e-mail] +1 -1
    Change www.mysql.com -> dev.mysql.com in a reference to
    how to resolve stack trace documentation.

ChangeSet
  1.2010.5.1 04/09/18 20:33:39 [e-mail] +4 -0
  bug#2831 - --extenral-locking does not fully work with --myisam-recover.
  Changed the semantics of open_count so that it is decremented
  at every unlock (if it was incremented due to data changes).
  So it indicates a crash, if it is non-zero after a lock.
  The table will then be repaired.

  sql/sql_table.cc
    1.186 04/09/18 20:33:37 [e-mail] +9 -3
    This does not really belong to the bugfix for #2831.
    But it was detected during fixing the external locking.

  sql/ha_myisam.cc
    1.131 04/09/18 20:33:37 [e-mail] +21 -3
    bug#2831 - --extenral-locking does not fully work with --myisam-recover.
    Added code to repair the table, if it is marked crashed after
    successful locking and the --myisam-recover option is set.

  myisam/mi_locking.c
    1.30 04/09/18 20:33:37 [e-mail] +79 -4
    bug#2831 - --extenral-locking does not fully work with --myisam-recover.
    open_count is now decremented at unlock (from a writelock) with
    mi_unlock_open_count(). After every new lock the state is read
    from the index file and the open_count checked. If not zero,
    another server must have crashed, so the table is marked as crashed.
    In certain situations the decremented open_count mut be flushed to
    the index file. I tried to keep these extra flushes as seldom as possible.

  myisam/mi_close.c
    1.14 04/09/18 20:33:37 [e-mail] +2 -1
    bug#2831 - --extenral-locking does not fully work with --myisam-recover.
    To avoid flushing the open_count at every unlock,
    we need to do so at close at least.

ChangeSet
  1.2022.1.1 04/09/18 13:06:44 [e-mail] +4 -0
  Fix for bug #5595: NULLIF() IS NULL returns false if NULLIF() returns NULL

  sql/item_cmpfunc.h
    1.33 04/09/18 13:06:42 [e-mail] +1 -0
    Fix for bug #5595: NULLIF() IS NULL returns false if NULLIF() returns NULL

  sql/item_cmpfunc.cc
    1.63 04/09/18 13:06:42 [e-mail] +9 -0
    Fix for bug #5595: NULLIF() IS NULL returns false if NULLIF() returns NULL

  mysql-test/t/func_if.test
    1.5 04/09/18 13:06:42 [e-mail] +4 -0
    Fix for bug #5595: NULLIF() IS NULL returns false if NULLIF() returns NULL

  mysql-test/r/func_if.result
    1.8 04/09/18 13:06:42 [e-mail] +3 -0
    Fix for bug #5595: NULLIF() IS NULL returns false if NULLIF() returns NULL

ChangeSet
  1.2023 04/09/17 17:16:02 [e-mail] +1 -0
  InnoDB: Corrected typos in DBUG_ statements

  sql/ha_innodb.cc
    1.221 04/09/17 17:15:51 [e-mail] +2 -2
    Corrected typos in DBUG_ statements

ChangeSet
  1.2022 04/09/17 12:07:59 [e-mail] +4 -0
  Bug#5553 - Multi table UPDATE IGNORE fails on dup key
    We don't want the update to abort when IGNORE is specified

  BitKeeper/etc/logging_ok
    1.325 04/09/17 12:07:58 [e-mail] +1 -0
    Logging to [e-mail] accepted

  sql/sql_update.cc
    1.101 04/09/17 12:07:54 [e-mail] +6 -2
    Bug#5553 - Multi table UPDATE IGNORE fails on dup key
      We don't want the update to abort when IGNORE is specified

  mysql-test/t/update.test
    1.12 04/09/17 12:07:54 [e-mail] +33 -0
    Bug#5553 - UPDATE IGNORE fails on dup key
      New test

  mysql-test/r/update.result
    1.13 04/09/17 12:07:54 [e-mail] +37 -0
    Bug#5553 - UPDATE IGNORE fails on dup key
      New test

ChangeSet
  1.2021 04/09/16 20:50:24 [e-mail] +4 -0
  dict0dict.h, dict0dict.c, row0row.c, pars0opt.c:
    Fix bug #5180: having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref()

  innobase/include/dict0dict.h
    1.27 04/09/16 20:50:02 [e-mail] +4 -2
    Fix bug #5180: having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref()

  innobase/dict/dict0dict.c
    1.59 04/09/16 20:49:53 [e-mail] +7 -3
    Fix bug #5180: having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref()

  innobase/row/row0row.c
    1.9 04/09/16 20:49:46 [e-mail] +34 -0
    Fix bug #5180: having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref()

  innobase/pars/pars0opt.c
    1.11 04/09/16 20:49:38 [e-mail] +13 -0
    Fix bug #5180: having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref()

ChangeSet
  1.2007.10.1 04/09/16 16:10:14 [e-mail] +1 -0
  Fixed Bug #5492 "set @@session.read_rnd_buffer_size=33554432"
     crashes server on query

  incremented size of allocated buffer in the init_rr_cache(sql/records.cc)
  (
  We are going to read the last three bytes of the buffer via uint3korr
  This macro reads actually 4 bytes (for speed)
  So, we have to allocate one more byte at the end of the buffer
  to avoid memory assertion fault
  )

  sql/records.cc
    1.22 04/09/16 16:10:07 [e-mail] +7 -1
    incremented size of allocated buffer in the init_rr_cache
    (
    We are going to read the last three bytes of the buffer via uint3korr
    This macro reads actually 4 bytes (for speed)
    So, we have to allocate one more byte at the end of the buffer
    to avoid memory assertion fault
    )
    Fixed Bug #5492 "set @@session.read_rnd_buffer_size=33554432"
      crashes server on query

ChangeSet
  1.2020 04/09/14 14:10:29 [e-mail] +1 -0
  another small change for bug 5531

  scripts/mysqlhotcopy.sh
    1.45 04/09/14 14:10:26 [e-mail] +1 -1
    one more \' to remove for bugfix 5531!

ChangeSet
  1.2019 04/09/14 12:23:18 [e-mail] +1 -0
  fixed bug 5531

  scripts/mysqlhotcopy.sh
    1.44 04/09/14 12:23:15 [e-mail] +1 -1
    small fix to help options per bug 5531

ChangeSet
  1.2015.2.2 04/09/13 20:08:09 [e-mail] +1 -0
  sync0arr.c:
    Correct the comment on the 'waiting' field in sync_cell_struct

  innobase/sync/sync0arr.c
    1.19 04/09/13 20:07:59 [e-mail] +1 -4
    Correct the comment on the 'waiting' field in sync_cell_struct

ChangeSet
  1.2015.2.1 04/09/13 19:05:39 [e-mail] +2 -0
  row0mysql.h:
    Improve the comment on stored_select_lock_type
  ha_innodb.cc:
    Let InnoDB remember select_lock_type inside LOCK TABLES, also over plain consistent read SELECTs; fix Bug #5538 : assertion failure when using mysqldump with the -l option; in MERGING this patch to 4.1, there may be PROBLEMS; that is because previous patch was never merged to 4.1; Heikki Tuuri has to polish the code in 4.1 after this patch has been merged.

  innobase/include/row0mysql.h
    1.21 04/09/13 19:01:34 [e-mail] +5 -3
    Improve the comment on stored_select_lock_type

  sql/ha_innodb.cc
    1.220 04/09/13 19:00:47 [e-mail] +38 -27
    Let InnoDB remember select_lock_type inside LOCK TABLES, also over plain consistent read SELECTs; fix Bug #5538 : assertion failure when using mysqldump with the -l option; in MERGING this patch to 4.1, there may be PROBLEMS; that is because previous patch was never merged to 4.1; Heikki Tuuri has to polish the code in 4.1 after this patch has been merged.

ChangeSet
  1.2015.1.1 04/09/13 14:25:43 [e-mail] +3 -0
  A fix (bug #5498 TRIM fails with LEADING or TRAILING if remstr = str).

  sql/item_strfunc.cc
    1.79 04/09/13 14:25:41 [e-mail] +3 -3
    A fix (bug #5498 TRIM fails with LEADING or TRAILING if remstr = str).

  mysql-test/t/func_str.test
    1.28 04/09/13 14:25:41 [e-mail] +7 -0
    A fix (bug #5498 TRIM fails with LEADING or TRAILING if remstr = str).

  mysql-test/r/func_str.result
    1.28 04/09/13 14:25:41 [e-mail] +6 -0
    A fix (bug #5498 TRIM fails with LEADING or TRAILING if remstr = str).

ChangeSet
  1.2016 04/09/13 12:13:24 hf@deer.(none) +1 -0
  Fix for bug #4809 (Backticks not handled in mysql)

  client/mysql.cc
    1.159 04/09/13 12:13:08 hf@deer.(none) +35 -3
    Code added to handle backticks

ChangeSet
  1.2015 04/09/11 09:37:16 [e-mail] +1 -0
  os0file.c:
    Add more precise diagnostics about the state of the I/O threads of InnoDB; print in SHOW INNODB STATUS if the event wait semaphore of each I/O thread is set

  innobase/os/os0file.c
    1.76 04/09/11 09:37:03 [e-mail] +16 -1
    Add more precise diagnostics about the state of the I/O threads of InnoDB; print in SHOW INNODB STATUS if the event wait semaphore of each I/O thread is set

ChangeSet
  1.2013 04/09/10 13:44:06 [e-mail] +1 -0
  dict0dict.c:
    Fixed typo

  innobase/dict/dict0dict.c
    1.58 04/09/10 13:43:51 [e-mail] +1 -1
    Fixed typo

ChangeSet
  1.2010.1.6 04/09/10 00:08:12 [e-mail] +2 -0
  configure.in:
    Updated to 4.0.22

  BitKeeper/etc/logging_ok
    1.324 04/09/10 00:08:12 [e-mail] +1 -0
    Logging to [e-mail] accepted

  configure.in
    1.314 04/09/10 00:07:23 [e-mail] +1 -1
    Updated to 4.0.22

ChangeSet
  1.2010.4.1 04/09/09 19:19:29 [e-mail] +1 -0
  Prevent some combinations of autotools and libtool version
  from generating a non-working top level 'libtool'.

  ltmain.sh
    1.13 04/09/09 19:17:46 [e-mail] +3 -0
    Some combinations of autotools and libtool leave 'max_cmd'len'
    (in top-level 'libtool') unset, this eventually causes a
    'ld' command without input files to be generated.
    Prevent this error by supplying a 4 kB default value.

ChangeSet
  1.2010.2.3 04/09/09 17:00:46 [e-mail] +2 -0
   - two small fixups for the mysql-copyright scripts: remove the
     autom4te.cache directory and update the headers of the message files.

  Build-tools/mysql-copyright
    1.16 04/09/09 17:00:39 [e-mail] +4 -0
     - remove the autom4te.cache directory (leftover from running
       autotools after modifying configure.in)

  Build-tools/mysql-copyright-2
    1.8 04/09/09 17:00:39 [e-mail] +1 -0
     - make sure to fix the copyright in the recently added GPL
       headers of the message files, too

ChangeSet
  1.2010.1.3 04/09/09 12:23:10 [e-mail] +3 -0
  Bug #5447 Select does not find records
  Note, there is no need to propagate this change into 4.1.

  strings/ctype-latin1_de.c
    1.10 04/09/09 12:23:08 [e-mail] +1 -1
    Bug #5447 Select does not find records

  mysql-test/t/ctype_latin1_de.test
    1.8 04/09/09 12:23:08 [e-mail] +14 -0
    Bug #5447 Select does not find records

  mysql-test/r/ctype_latin1_de.result
    1.9 04/09/09 12:23:08 [e-mail] +15 -0
    Bug #5447 Select does not find records

ChangeSet
  1.2010.3.1 04/09/08 18:26:19 [e-mail] +6 -0
  Updating the headers on a few files to include GPL header.

  BitKeeper/etc/logging_ok
    1.323 04/09/08 18:26:18 [e-mail] +1 -0
    Logging to [e-mail] accepted

  sql/sql_repl.h
    1.29 04/09/08 18:25:09 [e-mail] +16 -0
    Added license header

  sql/sql_repl.cc
    1.116 04/09/08 18:25:08 [e-mail] +0 -2
    Removed old maintainer.

  sql/slave.h
    1.77 04/09/08 18:25:08 [e-mail] +16 -0
    Added license header.

  sql/repl_failsafe.h
    1.8 04/09/08 18:25:08 [e-mail] +16 -0
    Added license header.

  sql/repl_failsafe.cc
    1.43 04/09/08 18:25:08 [e-mail] +0 -2
    Removed reference to old maintainer.

ChangeSet
  1.2010.2.1 04/09/08 16:31:01 [e-mail] +1 -0
  [This patch has already been approved by Serge.  I am recommitting and pushing from a new repository because there were other changesets that couldn't be pushed.]

  BUG# 5229 --password=foobar does not override the empty 'password' option in the my.cnf
  This is a backport of a change made by jani in the 4.1 tree.

  mysql.cc:
    Add tty_password=0 in the p case handling in get_one_option

  client/mysql.cc
    1.158 04/09/08 16:28:10 [e-mail] +1 -0
    Add tty_password=0 in the p case handling in get_one_option

ChangeSet
  1.2010.1.1 04/09/08 16:45:03 [e-mail] +1 -0
  A fix (bug #3120: 'mysqladmin ping' - return error code).

  client/mysqladmin.c
    1.76 04/09/08 16:44:55 [e-mail] +18 -3
    A fix (bug #3120: 'mysqladmin ping' - return error code).

ChangeSet
  1.2011 04/09/08 14:24:13 [e-mail] +9 -0
  InnoDB: Update links to the user manual

  innobase/ut/ut0dbg.c
    1.6 04/09/08 14:24:10 [e-mail] +3 -2
    Update links to the user manual

  innobase/row/row0mysql.c
    1.71 04/09/08 14:24:10 [e-mail] +12 -8
    Update links to the user manual

  innobase/os/os0file.c
    1.75 04/09/08 14:24:10 [e-mail] +19 -12
    Update links to the user manual

  innobase/log/log0recv.c
    1.32 04/09/08 14:24:09 [e-mail] +3 -3
    Update links to the user manual

  innobase/log/log0log.c
    1.37 04/09/08 14:24:09 [e-mail] +2 -3
    Update links to the user manual

  innobase/fsp/fsp0fsp.c
    1.24 04/09/08 14:24:09 [e-mail] +3 -3
    Update links to the user manual

  innobase/dict/dict0dict.c
    1.57 04/09/08 14:24:09 [e-mail] +6 -3
    Update links to the user manual

  innobase/buf/buf0buf.c
    1.33 04/09/08 14:24:09 [e-mail] +3 -3
    Update links to the user manual

  innobase/btr/btr0btr.c
    1.30 04/09/08 14:24:09 [e-mail] +2 -2
    Update links to the user manual

ChangeSet
  1.2009 04/09/07 10:03:46 [e-mail] +1 -0
  select.test:
    Added newline at the end of file.

  mysql-test/t/select.test
    1.24 04/09/07 10:03:01 [e-mail] +1 -1
    Added newline at the end of file.

ChangeSet
  1.2007.9.1 04/09/07 14:57:54 [e-mail] +3 -0
  when we update thd->db in replication, it's safer to update thd->db_length too.
  This does not fix any known bug, but is still a good idea.

  sql/sql_db.cc
    1.74 04/09/07 14:57:52 [e-mail] +9 -0
    comment

  sql/slave.cc
    1.283 04/09/07 14:57:51 [e-mail] +9 -4
    when we update thd->db in replication, it's safer to update thd->db_length too.

  sql/log_event.cc
    1.159 04/09/07 14:57:51 [e-mail] +10 -4
    when we update thd->db in replication, it's safer to update thd->db_length too.

ChangeSet
  1.2007.1.8 04/09/07 14:20:48 [e-mail] +2 -0
  clean up at end of test (thanks serg)

  mysql-test/t/rpl_set_charset.test
    1.3 04/09/07 14:20:46 [e-mail] +1 -3
    clean up on slave too.

  mysql-test/r/rpl_set_charset.result
    1.3 04/09/07 14:20:46 [e-mail] +0 -1
    result update

ChangeSet
  1.2007.1.7 04/09/07 13:48:38 [e-mail] +1 -0
  better fix for bug#5001

  scripts/mysqld_safe.sh
    1.71 04/09/07 13:48:32 [e-mail] +14 -23
    better fix for bug#5001

ChangeSet
  1.2007.1.6 04/09/07 13:36:27 [e-mail] +2 -0
  cleanup

  mysql-test/t/rpl_set_charset.test
    1.2 04/09/07 13:36:24 [e-mail] +2 -0
    cleanup

  mysql-test/r/rpl_set_charset.result
    1.2 04/09/07 13:36:24 [e-mail] +1 -0
    cleanup

ChangeSet
  1.2007.2.4 04/09/07 14:24:47 [e-mail] +1 -0
  A fix (Bug #5432: Is this a leak in mysql console client?)

  client/mysql.cc
    1.157 04/09/07 14:24:44 [e-mail] +4 -4
    A fix (Bug #5432: Is this a leak in mysql console client?)

ChangeSet
  1.2007.7.1 04/09/07 11:15:23 [e-mail] +2 -0
  A new test for the fix for BUG#4500 ("SET CHARACTER SET replicates incorrectly").
  As I cannot be 100% sure that there won't be issues with some of our exotic platforms
  (who knows if the charset of <obscure old OS> will play fair?), I'll send an email to the build guys.
  Well, this holds if bk does not crash on binary chars of this cset.

  mysql-test/t/rpl_set_charset.test
    1.1 04/09/07 11:15:20 [e-mail] +40 -0

  mysql-test/r/rpl_set_charset.result
    1.1 04/09/07 11:15:20 [e-mail] +51 -0

  mysql-test/t/rpl_set_charset.test
    1.0 04/09/07 11:15:20 [e-mail] +0 -0
    BitKeeper file /home/mysql_src/mysql-4.0/mysql-test/t/rpl_set_charset.test

  mysql-test/r/rpl_set_charset.result
    1.0 04/09/07 11:15:20 [e-mail] +0 -0
    BitKeeper file /home/mysql_src/mysql-4.0/mysql-test/r/rpl_set_charset.result

ChangeSet
  1.2007.3.6 04/09/07 11:40:27 [e-mail] +1 -0
  Fixed Bug#3645, "PROCEDURE ANALYSE() recommends illegal
  FLOAT columns".

  sql/sql_analyse.cc
    1.22 04/09/07 11:40:26 [e-mail] +7 -0
    Fixed Bug#3645, "PROCEDURE ANALYSE() recommends illegal
    FLOAT columns".

ChangeSet
  1.2007.3.5 04/09/06 23:20:33 [e-mail] +1 -0
  Fix of previous push.

  sql/sql_table.cc
    1.185 04/09/06 23:20:30 [e-mail] +2 -2
    stupid me. error already exists in the function. Using a local 'int error' resulted in global 'error' not being inited, which probably made next steps (those testing global error) go wrong!